← previous blocknext block →recent activity
Analyzing
Block #95,796,311
8 transactions · 7 stateful · 2026-08-14 02:19:44 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,796,311 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf0fabff3…9077
0x065c9d…c394
3 touches
1 conflict
0x2a6d5604…5d66
0x065c9d…c394
3 touches
1 conflict
0x592f9623…1e5a
0x1efe02…37d6
2 touches
0 conflicts
0x5b13c5a9…6eee
0x1efe02…37d6
2 touches
0 conflicts
0xc1659c91…b521
0x1efe02…37d6
2 touches
0 conflicts
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
1 conflict on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity