← previous blocknext block →recent activity
Analyzing
Block #95,524,111
12 transactions · 12 stateful · 2026-08-13 03:29:37 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,524,111 · 12 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
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a95ba16…0c9e
0x34b655…2a6f
4 touches
1 conflict
0x16e75abd…f3ad
0x34b655…2a6f
4 touches
1 conflict
0xda5977c4…2b61
0x34b655…2a6f
4 touches
1 conflict
0xf30b9357…2e1e
0x34b655…2a6f
4 touches
1 conflict
0x2b8c5b87…0cac
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x4e621c19…6089
0x34b655…2a6f
2 touches
0 conflicts
0x8c4c1c16…2c7d
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 0x6a95ba162d…c40c9e
Audit this contract →
← previous block·next block →recent activity