← previous blocknext block →recent activity
Analyzing
Block #97,604,360
14 transactions · 13 stateful · 2026-08-20 10:42:36 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,604,360 · 14 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
1w03w04w15w16w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x214dc988…ba27
0x34b655…2a6f
4 touches
1 conflict
0xe6bc2705…d15b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x40be70d4…6722
0x34b655…2a6f
2 touches
0 conflicts
0x55feaf48…4260
0x34b655…2a6f
2 touches
0 conflicts
0x775c0075…6c82
0x34b655…2a6f
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
1 conflict on slot 0x214dc98868…30ba27
Audit this contract →
← previous block·next block →recent activity