← previous blocknext block →recent activity
Analyzing
Block #104,159,128
24 transactions · 23 stateful · 2026-09-12 10:44:06 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,159,128 · 24 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
8w010w111w012w220w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe78db488…80f8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x66608f6c…12ad
0x34b655…2a6f
4 touches
1 conflict
0x7aa5d2c4…d6ef
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
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 0xe78db48806…4e80f8
Audit this contract →
← previous block·next block →recent activity