← previous blocknext block →recent activity
Analyzing
Block #97,615,032
19 transactions · 17 stateful · 2026-08-20 11:36:52 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,615,032 · 19 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
1w02w14w05w16w27w18w19w210w315w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x318ac0bb…6b9c
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xbfeef6e6…44f4
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x07b5c6c6…8866
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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
6 conflicts on slot 0x318ac0bba0…ce6b9c
Audit this contract →
← previous block·next block →recent activity