← previous blocknext block →recent activity
Analyzing
Block #96,554,242
9 transactions · 6 stateful · 2026-08-16 17:52:42 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,554,242 · 9 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b37bb6b…aaff
0x34b655…2a6f
6 touches
3 conflicts
0xfee9b27f…c06a
0x34b655…2a6f
4 touches
1 conflict
0x8a1e429b…f85c
0x34b655…2a6f
4 touches
1 conflict
0xa927d4ed…bf43
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc799e56d…45aa
0x34b655…2a6f
4 touches
1 conflict
0xe181f491…f4e3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x5b37bb6bbf…0aaaff
Audit this contract →
← previous block·next block →recent activity