← previous blocknext block →recent activity
Analyzing
Block #96,836,417
11 transactions · 10 stateful · 2026-08-17 17:31:57 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,836,417 · 11 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
1w02w15w08w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf29db88e…d471
0x34b655…2a6f
4 touches
1 conflict
0x3cb4b659…f735
0x34b655…2a6f
4 touches
1 conflict
0xdb5c0730…e75d
0x34b655…2a6f
4 touches
1 conflict
0xe52da074…4dc0
0x34b655…2a6f
4 touches
1 conflict
0xe8377f79…5f5e
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
6 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity