← previous blocknext block →recent activity
Analyzing
Block #99,494,240
21 transactions · 16 stateful · 2026-08-27 02:20:45 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,494,240 · 21 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
2w04w16w28w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0x8b98c194…d69e
0x851145…3f07
4 touches
1 conflict
0xa45be29d…8019
0x851145…3f07
4 touches
1 conflict
0xeffd747c…6a01
0x851145…3f07
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
4 touches
1 conflict
0x5a409e7f…09b6
0x2b46c0…1669
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