← previous blocknext block →recent activity
Analyzing
Block #97,386,181
20 transactions · 14 stateful · 2026-08-19 16:06:49 UTC
Parallelism
90/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,386,181 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w113w015w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb56619b…1b27
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0009
0x1e240e…10d4
2 touches
0 conflicts
0x00000000…f44c
0x1e240e…10d4
2 touches
0 conflicts
0x428bdbbe…3ec8
0x1e240e…10d4
2 touches
0 conflicts
0x06ce5d4b…c122
0x2b46c0…1669
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 0xbb56619baa…321b27
Audit this contract →
← previous block·next block →recent activity