← previous blocknext block →recent activity
Analyzing
Block #97,819,360
17 transactions · 16 stateful · 2026-08-21 04:56:06 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,819,360 · 17 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
2w04w05w16w17w210w211w113w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7975e059…379b
0x34b655…2a6f
6 touches
3 conflicts
0xaaa40a27…27cd
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xcdcab72a…f730
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3686cc89…4ffc
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x7975e0597e…c8379b
Audit this contract →
← previous block·next block →recent activity