← previous blocknext block →recent activity
Analyzing
Block #97,493,707
14 transactions · 13 stateful · 2026-08-20 01:23:30 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,493,707 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w06w18w19w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x713db58f…6ff9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x10f4217c…a84a
0x851145…3f07
4 touches
1 conflict
0x07c21ad6…3bfd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0x713db58fc3…1d6ff9
Audit this contract →
← previous block·next block →recent activity