← previous blocknext block →recent activity
Analyzing
Block #98,538,079
18 transactions · 16 stateful · 2026-08-23 17:33:44 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,538,079 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w110w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x59fbec8a…d5c0
0x065c9d…c394
3 touches
1 conflict
0x4963bc40…b829
0x065c9d…c394
3 touches
1 conflict
0xb5ed555a…386f
0x3bd359…433a
2 touches
0 conflicts
0x51378cb6…16b4
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity