← previous blocknext block →recent activity
Analyzing
Block #97,909,729
27 transactions · 24 stateful · 2026-08-21 12:39:16 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,909,729 · 27 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
2w03w14w26w07w18w210w311w012w013w114w216w118w019w220w121w326w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
8 touches
6 conflicts
0x526c29c3…6e50
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0003
0x103de0…bb55
4 touches
1 conflict
0x00000000…0005
0x103de0…bb55
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
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: 0x103de0b5…25bb55
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity