← previous blocknext block →recent activity
Analyzing
Block #95,214,834
16 transactions · 16 stateful · 2026-08-12 01:20:25 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,214,834 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b987499…a00c
0x34b655…2a6f
4 touches
1 conflict
0xcffc8fcf…ff81
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
0x96dd83e6…a507
0x34b655…2a6f
2 touches
0 conflicts
0x9ae859db…2d84
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 0x7b9874991a…5ca00c
Audit this contract →
← previous block·next block →recent activity