← previous blocknext block →recent activity
Analyzing
Block #96,706,674
17 transactions · 13 stateful · 2026-08-17 06:39:23 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,706,674 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w212w113w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf1cc9519…84c1
0x34b655…2a6f
8 touches
6 conflicts
0xe2274128…e5de
0x34b655…2a6f
6 touches
3 conflicts
0x04f6d949…d859
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x3522af60…d679
0x34b655…2a6f
4 touches
1 conflict
0x02060180…fe50
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity