← previous blocknext block →recent activity
Analyzing
Block #104,024,562
33 transactions · 31 stateful · 2026-09-11 23:19:23 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
1.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,024,562 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w114w015w116w218w319w421w522w623w724w831w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
18 touches
36 conflicts
0xc6d445ec…8564
0x34b655…2a6f
18 touches
36 conflicts
0xa4f6516c…aad0
0x34b655…2a6f
18 touches
36 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
18 touches
36 conflicts
0xf1595b25…ef40
0x34b655…2a6f
16 touches
28 conflicts
0xc7954a60…d294
0x34b655…2a6f
16 touches
28 conflicts
0x61ca6437…2142
0x34b655…2a6f
14 touches
21 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity