← previous blocknext block →recent activity
Analyzing
Block #96,030,265
10 transactions · 8 stateful · 2026-08-14 21:56:57 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,030,265 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fb89e5…b3c8
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0x121086b9…c565
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
0x34b655…2a6f
2 touches
0 conflicts
0x52ad6369…8a39
0x34b655…2a6f
2 touches
0 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
2 touches
0 conflicts
0x5fab7fbe…1ce5
0x34b655…2a6f
2 touches
0 conflicts
0x67054426…0a28
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xb7fb89e532…02b3c8
Audit this contract →
← previous block·next block →recent activity