← previous blocknext block →recent activity
Analyzing
Block #97,539,354
17 transactions · 17 stateful · 2026-08-20 05:13:08 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,539,354 · 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
1w07w09w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c0dcd35…3d69
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x59a84baf…4dfa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x0012270b…67b2
0x34b655…2a6f
2 touches
0 conflicts
0x10b99fca…1ebb
0x34b655…2a6f
2 touches
0 conflicts
0x3c6a6f0b…1b66
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 0x6c0dcd35b3…323d69
Audit this contract →
← previous block·next block →recent activity