← previous blocknext block →recent activity
Analyzing
Block #94,475,388
13 transactions · 13 stateful · 2026-08-09 11:18:49 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,475,388 · 13 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
2w03w04w15w16w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9a321bc…88d5
0x34b655…2a6f
4 touches
1 conflict
0x2021fb2a…d63c
0x34b655…2a6f
4 touches
1 conflict
0x22866298…d604
0x34b655…2a6f
4 touches
1 conflict
0x2592d715…a50e
0x34b655…2a6f
4 touches
1 conflict
0x3cee2479…edb8
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0x53a7ea0d…090f
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
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 0xe9a321bcb2…d388d5
Audit this contract →
← previous block·next block →recent activity