← previous blocknext block →recent activity
Analyzing
Block #97,467,206
13 transactions · 11 stateful · 2026-08-19 23:09:56 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,467,206 · 13 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8766b46f…c9b2
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x260cc5c4…bef0
0x2b46c0…1669
2 touches
0 conflicts
0x3a3e7727…36c5
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186d
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186e
0x2b46c0…1669
2 touches
0 conflicts
0x8b2c44b4…7e59
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 0x8766b46f1a…95c9b2
Audit this contract →
← previous block·next block →recent activity