← previous blocknext block →recent activity
Analyzing
Block #104,333,880
10 transactions · 10 stateful · 2026-09-13 01:30:40 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,333,880 · 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
2w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xad9f7641…a4ff
0x34b655…2a6f
4 touches
1 conflict
0x1bd5e8fa…471f
0x34b655…2a6f
2 touches
0 conflicts
0x3a2ca9cb…3fa4
0x34b655…2a6f
2 touches
0 conflicts
0x3af23ac1…47b5
0x34b655…2a6f
2 touches
0 conflicts
0x3b80be03…9bce
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity