← previous blocknext block →recent activity
Analyzing
Block #97,479,867
9 transactions · 9 stateful · 2026-08-20 00:13:53 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,479,867 · 9 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
1w02w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x59a84baf…4dfa
0x34b655…2a6f
4 touches
1 conflict
0x0c2765b4…a101
0x34b655…2a6f
4 touches
1 conflict
0xda1f3e2c…b73d
0x34b655…2a6f
4 touches
1 conflict
0x6235fbc3…aa1e
0x34b655…2a6f
2 touches
0 conflicts
0x77a5bf9e…fca7
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x08cc68a2c8…482a59
Audit this contract →
← previous block·next block →recent activity