← previous blocknext block →recent activity
Analyzing
Block #104,024,301
22 transactions · 19 stateful · 2026-09-11 23:18:03 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,024,301 · 22 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
3w08w012w013w114w216w317w118w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x193ae613…7b3a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
0x34b655…2a6f
4 touches
1 conflict
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x316ec1a9…40de
0x34b655…2a6f
4 touches
1 conflict
0x36cfb788…a2b0
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
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 0x193ae613c9…237b3a
Audit this contract →
← previous block·next block →recent activity