← previous blocknext block →recent activity
Analyzing
Block #98,648,424
21 transactions · 21 stateful · 2026-08-24 03:08:40 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,648,424 · 21 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
1w04w05w16w27w39w010w113w014w115w216w317w418w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x059ae4fe…ea63
0xa6afd3…d132
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity