← previous blocknext block →recent activity
Analyzing
Block #97,478,764
14 transactions · 13 stateful · 2026-08-20 00:08:20 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,478,764 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w18w09w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc86774…166a
0x34b655…2a6f
4 touches
1 conflict
0x75fe24d2…46f9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x6737ee07…9978
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
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: Perpl
1 conflict on slot 0x1dc86774a8…36166a
Audit this contract →
← previous block·next block →recent activity