← previous blocknext block →recent activity
Analyzing
Block #104,024,637
9 transactions · 9 stateful · 2026-09-11 23:19:45 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,024,637 · 9 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
2w05w06w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c68c214…1b34
0x34b655…2a6f
6 touches
3 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0x61ca6437…2142
0x34b655…2a6f
4 touches
1 conflict
0xa002a210…be6d
0x34b655…2a6f
4 touches
1 conflict
0x2b0a16b3…11de
0x34b655…2a6f
2 touches
0 conflicts
0x2c0fe9aa…dad9
0x34b655…2a6f
2 touches
0 conflicts
0x6f0906cb…c7e5
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 0x3c68c21456…dd1b34
Audit this contract →
← previous block·next block →recent activity