← previous blocknext block →recent activity
Analyzing
Block #95,718,814
10 transactions · 9 stateful · 2026-08-13 19:49:59 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,718,814 · 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
2w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x49bb2275…35ba
0x34b655…2a6f
3 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
2 touches
0 conflicts
0x8b2c44b4…7e59
0x2b46c0…1669
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 0x784eaad228…0ad176
Audit this contract →
← previous block·next block →recent activity