← previous blocknext block →recent activity
Analyzing
Block #104,024,340
21 transactions · 18 stateful · 2026-09-11 23:18:14 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,024,340 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w17w210w313w214w315w417w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcea5e966…88fd
0x34b655…2a6f
10 touches
10 conflicts
0x100812e9…12b7
0x34b655…2a6f
6 touches
3 conflicts
0x30908823…a62d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x7bc897a6…b1b7
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0xaaae2ec0…60a6
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
10 conflicts on slot 0xcea5e9660d…8188fd
Audit this contract →
← previous block·next block →recent activity