← previous blocknext block →recent activity
Analyzing
Block #104,033,528
10 transactions · 10 stateful · 2026-09-12 00:04:50 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,033,528 · 10 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
3w05w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec37efb4…f355
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x10379e8d…3675
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 conflicts
0x2d8487d0…24c6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xec37efb4cb…76f355
Audit this contract →
← previous block·next block →recent activity