← previous blocknext block →recent activity
Analyzing
Block #104,192,282
20 transactions · 17 stateful · 2026-09-12 13:32:10 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,192,282 · 20 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
1w011w113w014w115w116w117w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdafa2b8a…d648
0x34b655…2a6f
4 touches
1 conflict
0xf1231bea…990b
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x73a33694…9d5d
0x34b655…2a6f
4 touches
1 conflict
0xa065de59…3f32
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xdf08af9e…1985
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xdafa2b8a6f…4bd648
Audit this contract →
← previous block·next block →recent activity