← previous blocknext block →recent activity
Analyzing
Block #95,726,795
14 transactions · 13 stateful · 2026-08-13 20:30:07 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,726,795 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w19w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xc56b390b…e0ce
0x34b655…2a6f
4 touches
1 conflict
0x4cf86968…e398
0x34b655…2a6f
4 touches
1 conflict
0xba0aa618…04aa
0x34b655…2a6f
4 touches
1 conflict
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4cb450ac…4047
0x34b655…2a6f
4 touches
1 conflict
0xb444b9b5…9c7b
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
3 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity