← previous blocknext block →recent activity
Analyzing
Block #94,466,474
11 transactions · 9 stateful · 2026-08-09 10:33:55 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,466,474 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x22866298…d604
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x5a8986a5…f3b7
0x065c9d…c394
3 touches
1 conflict
0xd6c6dcfb…677c
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 0x3d93ad2c39…a6e747
Audit this contract →
← previous block·next block →recent activity