← previous blocknext block →recent activity
Analyzing
Block #97,519,548
28 transactions · 23 stateful · 2026-08-20 03:33:30 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,519,548 · 28 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
3w04w08w09w110w011w112w113w214w218w219w320w321w422w523w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x1ba73d09…ba89
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xf3ed0f92…bd2a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x38c47502…1005
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity