← previous blocknext block →recent activity
Analyzing
Block #98,641,956
14 transactions · 8 stateful · 2026-08-24 02:35:05 UTC
Parallelism
86/100
Blocked
13%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,641,956 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x53e532d2…69e0
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0000
0x08cb87…f271
2 touches
0 conflicts
0x0e75c51c…e337
0x08cb87…f271
2 touches
0 conflicts
0x59f8f49f…a292
0x08cb87…f271
2 touches
0 conflicts
0xba35282c…6beb
0x08cb87…f271
2 touches
0 conflicts
0xee1dbda3…37c3
0x08cb87…f271
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