← previous blocknext block →recent activity
Analyzing
Block #100,620,353
22 transactions · 18 stateful · 2026-08-31 01:06:04 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,620,353 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w211w013w114w316w117w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16ebf93b…ce00
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2a3a1679…b3ef
0x34b655…2a6f
6 touches
3 conflicts
0xd4c913d7…343f
0x1b6862…e19c
6 touches
3 conflicts
0xf01185a0…d96e
0xd32edf…ff58
5 touches
3 conflicts
0x00500a94…20d5
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 0x16ebf93bf3…87ce00
Audit this contract →
← previous block·next block →recent activity