← previous blocknext block →recent activity
Analyzing
Block #99,020,062
12 transactions · 11 stateful · 2026-08-25 10:29:23 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,020,062 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x65b1e075…7a54
0x34b655…2a6f
2 touches
0 conflicts
0x91b8c157…148e
0x34b655…2a6f
2 touches
0 conflicts
0x99e78c69…b11f
0x34b655…2a6f
2 touches
0 conflicts
0x9c6a9da2…c628
0x34b655…2a6f
2 touches
0 conflicts
0xa6a0c2dd…b797
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity