← previous blocknext block →recent activity
Analyzing
Block #101,668,809
10 transactions · 8 stateful · 2026-09-03 17:01:28 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,668,809 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0xce593d83…ea8b
0x34b655…2a6f
4 touches
1 conflict
0x1a04fff3…c30a
0x34b655…2a6f
2 touches
0 conflicts
0x2aab0897…78f7
0x34b655…2a6f
2 touches
0 conflicts
0x4089d428…b018
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity