← previous blocknext block →recent activity
Analyzing
Block #104,033,629
11 transactions · 10 stateful · 2026-09-12 00:05:21 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,033,629 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w18w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda50c9d5…674e
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6e5d9b07…ceac
0x34b655…2a6f
4 touches
1 conflict
0x9301a8d9…fdad
0x34b655…2a6f
4 touches
1 conflict
0xc6b75e8a…fae8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x24b08f9c…e594
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 0xda50c9d58b…78674e
Audit this contract →
← previous block·next block →recent activity