← previous blocknext block →recent activity
Analyzing
Block #99,975,595
21 transactions · 18 stateful · 2026-08-28 18:57:27 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,975,595 · 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
1w02w14w19w010w211w012w113w218w019w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfbeb21…92b1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0161566e…abb2
0xa6afd3…d132
6 touches
3 conflicts
0x37699b20…1071
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1fb8364c…c10d
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: Perpl
3 conflicts on slot 0x5cfbeb217d…8e92b1
Audit this contract →
← previous block·next block →recent activity