← previous blocknext block →recent activity
Analyzing
Block #95,524,448
19 transactions · 17 stateful · 2026-08-13 03:31:18 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,524,448 · 19 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
3w04w05w16w07w18w29w310w411w513w614w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a9e9bd1…5368
0x2a68ba…90c5
14 touches
21 conflicts
0xba7cc460…9e30
0xa6afd3…d132
13 touches
21 conflicts
0x11b69a7e…334e
0xee8c0e…1242
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
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: Kuru Exchange: MarginAccount
21 conflicts on slot 0x2a9e9bd1e2…355368
Audit this contract →
← previous block·next block →recent activity