← previous blocknext block →recent activity
Analyzing
Block #97,519,031
19 transactions · 17 stateful · 2026-08-20 03:30:54 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,519,031 · 19 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
1w02w13w05w06w17w18w211w312w416w517w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95f0b212…5f7a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x5caf9f43…a348
0x34b655…2a6f
6 touches
3 conflicts
0xfe2c1082…db16
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2267f8c4…a571
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
3 conflicts on slot 0x95f0b21248…e95f7a
Audit this contract →
← previous block·next block →recent activity