← previous blocknext block →recent activity
Analyzing
Block #97,493,914
16 transactions · 14 stateful · 2026-08-20 01:24:32 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,493,914 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w010w111w112w213w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc04ab655…ed73
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xda1f3e2c…b73d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x178fe051…465a
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 0xc04ab6557a…0ced73
Audit this contract →
← previous block·next block →recent activity