← previous blocknext block →recent activity
Analyzing
Block #95,125,040
13 transactions · 12 stateful · 2026-08-11 17:48:46 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,125,040 · 13 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xc0ab38cc…600c
0x34b655…2a6f
4 touches
1 conflict
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0x9f9a2d80…d055
0x34b655…2a6f
4 touches
1 conflict
0x2acf7e76…bbe8
0x34b655…2a6f
2 touches
0 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
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 0x68c07cb991…56ae14
Audit this contract →
← previous block·next block →recent activity