← previous blocknext block →recent activity
Analyzing
Block #96,654,616
14 transactions · 13 stateful · 2026-08-17 02:17:33 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,654,616 · 14 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
1w02w03w16w27w311w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3a56380e…e955
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e88
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e89
0x34b655…2a6f
4 touches
1 conflict
0x619f6301…19b3
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity