← previous blocknext block →recent activity
Analyzing
Block #96,569,192
15 transactions · 15 stateful · 2026-08-16 19:07:54 UTC
Parallelism
47/100
Blocked
60%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,569,192 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w17w38w49w510w611w714w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
16 touches
28 conflicts
0x34b1e500…7687
0x754704…b603
16 touches
28 conflicts
0x00000000…000b
0x78999c…f371
16 touches
28 conflicts
0x00000000…000f
0x78999c…f371
16 touches
28 conflicts
0x00000000…000b
0x754704…b603
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9719e4fc…0cda
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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: 0x00000000…7da032
28 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity