← previous blocknext block →recent activity
Analyzing
Block #97,851,731
21 transactions · 19 stateful · 2026-08-21 07:40:56 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,851,731 · 21 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
1w02w03w14w05w16w17w28w311w012w413w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf496f80c…d5c8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x1a2055c7…9054
0x34b655…2a6f
4 touches
1 conflict
0x1a2055c7…9055
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x629e09e5…692a
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
3 conflicts on slot 0xf496f80c95…3ed5c8
Audit this contract →
← previous block·next block →recent activity