← previous blocknext block →recent activity
Analyzing
Block #96,154,324
19 transactions · 19 stateful · 2026-08-15 08:21:01 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,154,324 · 19 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
1w02w13w25w06w18w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1ec3b83…5320
0x968279…9342
4 touches
1 conflict
0x06e3cc17…6a23
0x968279…9342
4 touches
1 conflict
0x06e3cc17…6a25
0x968279…9342
4 touches
1 conflict
0xe1ec3b83…5319
0x968279…9342
4 touches
1 conflict
0xe1ec3b83…531a
0x968279…9342
4 touches
1 conflict
0xe1ec3b83…531d
0x968279…9342
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity