← previous blocknext block →recent activity
Analyzing
Block #97,493,566
9 transactions · 8 stateful · 2026-08-20 01:22:47 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,493,566 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0xda1f3e2c…b73d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x69196d53…b31c
0x34b655…2a6f
4 touches
1 conflict
0x1e8e485d…ced9
0x34b655…2a6f
2 touches
0 conflicts
0x251392a4…4a99
0x34b655…2a6f
2 touches
0 conflicts
0x2d9e167d…d3f8
0x34b655…2a6f
2 touches
0 conflicts
0x3750b746…5a9e
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xf346808d47…866ad4
Audit this contract →
← previous block·next block →recent activity