← previous blocknext block →recent activity
Analyzing
Block #102,409,600
7 transactions · 7 stateful · 2026-09-06 07:27:38 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,409,600 · 7 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2d23d3…8a3a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0x0259de4d…a4dd
0x34b655…2a6f
2 touches
0 conflicts
0x07c75224…b5a5
0x34b655…2a6f
2 touches
0 conflicts
0x0c12037c…7c96
0x34b655…2a6f
2 touches
0 conflicts
0x1b5b0c97…d824
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
1 conflict on slot 0x0d2d23d3eb…148a3a
Audit this contract →
← previous block·next block →recent activity