← previous blocknext block →recent activity
Analyzing
Block #98,723,912
35 transactions · 25 stateful · 2026-08-24 09:37:18 UTC
Parallelism
89/100
Blocked
48%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,723,912 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w19w010w116w117w218w219w020w123w224w128w029w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x34a6f177…8549
0x40c49f…2af0
5 touches
3 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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: MarginAccount
3 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity