← previous blocknext block →recent activity
Analyzing
Block #101,673,407
9 transactions · 9 stateful · 2026-09-03 17:24:36 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,673,407 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa44f1db…0666
0x34b655…2a6f
4 touches
1 conflict
0x0ac3888a…93e2
0x34b655…2a6f
4 touches
1 conflict
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x3a02129f…9eaf
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x448fdf2a…fab4
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
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
1 conflict on slot 0xfa44f1dbb9…dd0666
Audit this contract →
← previous block·next block →recent activity