← previous blocknext block →recent activity
Analyzing
Block #95,809,495
18 transactions · 16 stateful · 2026-08-14 03:26:03 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,809,495 · 18 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
1w02w14w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9bbb26e8…0d2e
0x99c7a7…8bf0
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0x8ee86cb5…db9c
0x99c7a7…8bf0
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity