← previous blocknext block →recent activity
Analyzing
Block #99,957,352
23 transactions · 22 stateful · 2026-08-28 17:25:34 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,957,352 · 23 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
1w02w03w14w25w36w17w210w012w117w018w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x912009…bb53
8 touches
6 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0xa12c6e18…150e
0x34b655…2a6f
6 touches
3 conflicts
0xdbaa5cd2…6a54
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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: 0x9120090c…dfbb53
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity