← previous blocknext block →recent activity
Analyzing
Block #98,506,670
12 transactions · 12 stateful · 2026-08-23 14:49:48 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,506,670 · 12 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
1w02w03w15w06w17w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x0c428e…07a4
4 touches
1 conflict
0x20b50479…b75c
0x0158ab…1a70
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2cef1eff…9f14
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x68e5627d…6f8f
0x34b655…2a6f
4 touches
1 conflict
0x50b4806e…c048
0x3bd359…433a
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity