← previous blocknext block →recent activity
Analyzing
Block #101,802,123
18 transactions · 15 stateful · 2026-09-04 04:12:00 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,802,123 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w07w110w213w315w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f0f10dd…05bd
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
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 0x0f0f10ddf5…a405bd
Audit this contract →
← previous block·next block →recent activity