← previous blocknext block →recent activity
Analyzing
Block #95,369,859
32 transactions · 23 stateful · 2026-08-12 14:32:02 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.66
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,369,859 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w19w014w119w120w121w222w323w429w130w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b638a0…761d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…343e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00ddbbf2…4588
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 0x27b638a069…8e761d
Audit this contract →
← previous block·next block →recent activity