← previous blocknext block →recent activity
Analyzing
Block #94,481,063
13 transactions · 11 stateful · 2026-08-09 11:47:21 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,481,063 · 13 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
2w03w14w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16838830…6ab2
0x34b655…2a6f
4 touches
1 conflict
0x23eeba48…cc51
0x34b655…2a6f
4 touches
1 conflict
0x23eeba48…cc52
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x7265fa19…9534
0x34b655…2a6f
4 touches
1 conflict
0xd0aebe26…167d
0x34b655…2a6f
4 touches
1 conflict
0xd6abb553…1d08
0x34b655…2a6f
4 touches
1 conflict
0xf17c63a1…a36b
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
1 conflict on slot 0x16838830d5…0c6ab2
Audit this contract →
← previous block·next block →recent activity