← previous blocknext block →recent activity
Analyzing
Block #95,902,819
18 transactions · 17 stateful · 2026-08-14 11:15:38 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,902,819 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w311w412w513w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a5ced1c…3b29
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x099f54bd…3e50
0x34b655…2a6f
8 touches
6 conflicts
0xadc05b3e…378d
0x34b655…2a6f
8 touches
6 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
6 touches
3 conflicts
0x97862f28…4ede
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
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
15 conflicts on slot 0x8a5ced1cae…443b29
Audit this contract →
← previous block·next block →recent activity