← previous blocknext block →recent activity
Analyzing
Block #95,300,063
16 transactions · 14 stateful · 2026-08-12 08:38:27 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,300,063 · 16 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
1w02w03w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x0b0ed9fe…4b57
0x34b655…2a6f
2 touches
0 conflicts
0x3a2b650f…f454
0x34b655…2a6f
2 touches
0 conflicts
0x421d159c…da4e
0x34b655…2a6f
2 touches
0 conflicts
0x465ce74f…39c8
0x34b655…2a6f
2 touches
0 conflicts
0x69c491e3…98d9
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 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity