← previous blocknext block →recent activity
Analyzing
Block #99,484,178
10 transactions · 10 stateful · 2026-08-27 01:30:05 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,484,178 · 10 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
1w02w13w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3ad04ce1…1904
0xa6afd3…d132
4 touches
1 conflict
0x37f5d54e…a6dd
0xa6afd3…d132
4 touches
1 conflict
0xdb40334f…e0bc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xba3549b9…683a
0xa6afd3…d132
3 touches
1 conflict
0xec360c87…8c77
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
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