← previous blocknext block →recent activity
Analyzing
Block #104,321,513
16 transactions · 13 stateful · 2026-09-13 00:27:54 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,321,513 · 16 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
1w02w15w07w113w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe66201d4…84f1
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x14084a98…58b3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x845baaac…a8ea
0x34b655…2a6f
5 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0x6f232437…749d
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 0xe66201d40c…1e84f1
Audit this contract →
← previous block·next block →recent activity