← previous blocknext block →recent activity
Analyzing
Block #98,430,620
23 transactions · 20 stateful · 2026-08-23 08:25:30 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,430,620 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w08w19w010w214w116w118w019w121w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6515cea…f915
0x065c9d…c394
5 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xe6515cea35…8ef915
Audit this contract →
← previous block·next block →recent activity