← previous blocknext block →recent activity
Analyzing
Block #96,664,963
12 transactions · 12 stateful · 2026-08-17 03:09:36 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,664,963 · 12 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
1w02w03w14w05w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xf1345bef…5530
0x34b655…2a6f
6 touches
3 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xe29938de…46f1
0x34b655…2a6f
4 touches
1 conflict
0xe2ca9bf2…8da8
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0xb2fa1675e0…3c4e07
Audit this contract →
← previous block·next block →recent activity