← previous blocknext block →recent activity
Analyzing
Block #98,383,433
16 transactions · 14 stateful · 2026-08-23 04:28:05 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,383,433 · 16 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
1w02w03w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4031a05…c53d
0x065c9d…c394
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x2ab9baf1…a394
0x34b655…2a6f
2 touches
0 conflicts
0x62030a81…91be
0x34b655…2a6f
2 touches
0 conflicts
0x7dc1eff1…ebac
0x34b655…2a6f
2 touches
0 conflicts
0x51ca3051…0972
0x3bd359…433a
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: Market-MON/USDC
1 conflict on slot 0xd4031a0558…dcc53d
Audit this contract →
← previous block·next block →recent activity