← previous blocknext block →recent activity
Analyzing
Block #97,819,730
17 transactions · 17 stateful · 2026-08-21 04:57:59 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,819,730 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w28w39w410w511w613w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe6d0f1c…20a0
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xaaa40a27…27cd
0x34b655…2a6f
6 touches
3 conflicts
0x3686cc89…4ffc
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe3663326…08d9
0x34b655…2a6f
6 touches
3 conflicts
0x3cd6f7af…4a43
0xa6afd3…d132
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
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
6 conflicts on slot 0xbe6d0f1c2c…7b20a0
Audit this contract →
← previous block·next block →recent activity