← previous blocknext block →recent activity
Analyzing
Block #97,552,716
17 transactions · 16 stateful · 2026-08-20 06:20:49 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,552,716 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w011w114w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x6cf4ede1…42fc
0x34b655…2a6f
4 touches
1 conflict
0x9b1f19e6…c5bf
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x31532dc6…db47
0x34b655…2a6f
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 0x00f245ce7e…641e10
Audit this contract →
← previous block·next block →recent activity