← previous blocknext block →recent activity
Analyzing
Block #97,816,695
16 transactions · 13 stateful · 2026-08-21 04:42:29 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,816,695 · 16 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
6w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0x2dbd1c87…a00e
0x34b655…2a6f
4 touches
1 conflict
0x2dee236d…7b30
0x34b655…2a6f
4 touches
1 conflict
0x5af6c596…a526
0x34b655…2a6f
4 touches
1 conflict
0x12f129f2…fe6b
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1867
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…186d
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 0x9c2fc33042…7d0091
Audit this contract →
← previous block·next block →recent activity