← previous blocknext block →recent activity
Analyzing
Block #97,551,698
19 transactions · 18 stateful · 2026-08-20 06:15:30 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,551,698 · 19 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
1w02w04w16w07w08w19w112w217w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c47502…1005
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
3 conflicts on slot 0x38c4750210…391005
Audit this contract →
← previous block·next block →recent activity