← previous blocknext block →recent activity
Analyzing
Block #97,684,726
19 transactions · 19 stateful · 2026-08-20 17:35:24 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,684,726 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w17w28w210w312w013w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b85d8e…1edd
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x88b255be…0308
0xa6afd3…d132
4 touches
1 conflict
0x00af64fb…9150
0x34b655…2a6f
4 touches
1 conflict
0x054c4679…2f2e
0x34b655…2a6f
4 touches
1 conflict
0x1390da55…bcd0
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
10 conflicts on slot 0x35b85d8e2a…641edd
Audit this contract →
← previous block·next block →recent activity