← previous blocknext block →recent activity
Analyzing
Block #97,518,159
17 transactions · 17 stateful · 2026-08-20 03:26:31 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,518,159 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w09w110w211w312w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38f2e1ca…e9d9
0x34b655…2a6f
6 touches
3 conflicts
0x95f0b212…5f7a
0x34b655…2a6f
6 touches
3 conflicts
0xeb0ee20b…d1e2
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
0x1003b807…2d24
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 0x38f2e1ca69…17e9d9
Audit this contract →
← previous block·next block →recent activity