← previous blocknext block →recent activity
Analyzing
Block #97,734,936
19 transactions · 18 stateful · 2026-08-20 21:49:56 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,734,936 · 19 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
1w03w05w110w013w116w017w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bc9b1ca…85ef
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x069074e9…0a9b
0x34b655…2a6f
2 touches
0 conflicts
0x06e7db76…ef34
0x34b655…2a6f
2 touches
0 conflicts
0x39b7fa08…6f3a
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 0x1bc9b1cade…5085ef
Audit this contract →
← previous block·next block →recent activity