← previous blocknext block →recent activity
Analyzing
Block #104,332,292
17 transactions · 16 stateful · 2026-09-13 01:22:36 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,332,292 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w210w112w213w315w016w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6df1d50f…8a92
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8cfa9962…2675
0x34b655…2a6f
4 touches
1 conflict
0xad9f7641…a4ff
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3222147c…8d93
0x34b655…2a6f
4 touches
1 conflict
0xddc5beb2…3f56
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
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
3 conflicts on slot 0x6df1d50f92…968a92
Audit this contract →
← previous block·next block →recent activity