← previous blocknext block →recent activity
Analyzing
Block #95,716,894
14 transactions · 13 stateful · 2026-08-13 19:40:19 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,716,894 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9538ea90…0536
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x990332f1…aae7
0x34b655…2a6f
4 touches
1 conflict
0xb4527790…c282
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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
1 conflict on slot 0x9538ea9015…e80536
Audit this contract →
← previous block·next block →recent activity