← previous blocknext block →recent activity
Analyzing
Block #98,100,983
31 transactions · 24 stateful · 2026-08-22 04:46:21 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,100,983 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w17w19w010w119w020w123w124w025w227w329w430w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0xf88ccd07…a684
0xa6afd3…d132
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity