← previous blocknext block →recent activity
Analyzing
Block #97,386,373
25 transactions · 23 stateful · 2026-08-19 16:08:17 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,386,373 · 25 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
2w03w04w05w16w17w211w312w413w516w117w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xa0bd005c…fd02
0xa6afd3…d132
6 touches
3 conflicts
0x30c5329c…711c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x5d9698ff…d8f9
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7215
0x34b655…2a6f
6 touches
3 conflicts
0x5e21b38a…09ef
0x34b655…2a6f
5 touches
3 conflicts
0x037a4023…1f5a
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity