← previous blocknext block →recent activity
Analyzing
Block #94,813,405
16 transactions · 15 stateful · 2026-08-10 15:40:26 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,813,405 · 16 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
1w02w03w15w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddb5d175…9fd9
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x45b4ae9c…dcf4
0x34b655…2a6f
2 touches
0 conflicts
0x52605a85…8853
0x34b655…2a6f
2 touches
0 conflicts
0x539ac47f…eb6f
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 0xddb5d1750a…839fd9
Audit this contract →
← previous block·next block →recent activity