← previous blocknext block →recent activity
Analyzing
Block #97,496,249
31 transactions · 27 stateful · 2026-08-20 01:36:17 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,496,249 · 31 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
1w02w04w05w16w17w28w29w311w013w414w515w516w121w129w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6737ee07…9978
0x34b655…2a6f
10 touches
10 conflicts
0x728f999a…832f
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x7e3213a0…1e47
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc2654d4e…8e94
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 0x6737ee07d3…1e9978
Audit this contract →
← previous block·next block →recent activity