← previous blocknext block →recent activity
Analyzing
Block #95,782,243
17 transactions · 14 stateful · 2026-08-14 01:08:59 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,782,243 · 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
2w03w14w28w39w410w411w512w613w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8eae8a3…bacc
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x43274fb7…08aa
0x34b655…2a6f
8 touches
6 conflicts
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x5484fc7f…a8d8
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xe8eae8a323…64bacc
Audit this contract →
← previous block·next block →recent activity