← previous blocknext block →recent activity
Analyzing
Block #98,327,127
23 transactions · 16 stateful · 2026-08-22 23:44:50 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,327,127 · 23 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
3w06w19w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x574bd04f…be57
0x065c9d…c394
4 touches
1 conflict
0x061b446e…d71c
0x40c49f…2af0
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0007
0x340143…768f
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity