← previous blocknext block →recent activity
Analyzing
Block #95,570,413
17 transactions · 15 stateful · 2026-08-13 07:22:29 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,570,413 · 17 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
2w03w04w15w27w39w410w511w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc683bfb0…3bbc
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a0a2b03…ac50
0x34b655…2a6f
4 touches
1 conflict
0x5e0a8339…3fa2
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
21 conflicts on slot 0xc683bfb0c1…9a3bbc
Audit this contract →
← previous block·next block →recent activity