← previous blocknext block →recent activity
Analyzing
Block #98,529,356
36 transactions · 27 stateful · 2026-08-23 16:48:25 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,529,356 · 36 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
1w02w09w110w014w115w216w318w020w221w329w030w431w432w133w134w035w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
6 touches
3 conflicts
0xe0c550f0…4264
0x851145…3f07
6 touches
3 conflicts
0x2dce1075…953a
0xd32edf…ff58
5 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity