← previous blocknext block →recent activity
Analyzing
Block #97,561,192
18 transactions · 14 stateful · 2026-08-20 07:04:07 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,561,192 · 18 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
3w06w013w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x10a2c7b4…5200
0x065c9d…c394
2 touches
0 conflicts
0x22ea9675…6b88
0x065c9d…c394
2 touches
0 conflicts
0x2b122179…55a7
0x065c9d…c394
2 touches
0 conflicts
0x3cc06649…ae62
0x065c9d…c394
2 touches
0 conflicts
0xa9f33448…8407
0x065c9d…c394
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 0x5d7e0e6938…45e6d2
Audit this contract →
← previous block·next block →recent activity