← previous blocknext block →recent activity
Analyzing
Block #95,744,218
14 transactions · 14 stateful · 2026-08-13 21:57:45 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,744,218 · 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
2w03w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6bc8db…0519
0x34b655…2a6f
8 touches
6 conflicts
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0x1b324d5c…a061
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
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 0x5f6bc8db1a…f60519
Audit this contract →
← previous block·next block →recent activity