← previous blocknext block →recent activity
Analyzing
Block #97,737,541
28 transactions · 22 stateful · 2026-08-20 22:03:03 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,737,541 · 28 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
1w02w14w05w06w17w08w09w110w211w212w313w414w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0xf6c9bf9b…ac02
0x34b655…2a6f
4 touches
1 conflict
0xa8436daa…788b
0xd32edf…ff58
3 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
6 conflicts on slot 0x69352f9f62…375449
Audit this contract →
← previous block·next block →recent activity