← previous blocknext block →recent activity
Analyzing
Block #97,466,665
24 transactions · 23 stateful · 2026-08-19 23:07:13 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,466,665 · 24 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
1w02w14w05w16w17w211w012w114w315w116w217w018w119w220w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x75fe24d2…46f9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x806c6904…3d63
0x34b655…2a6f
6 touches
3 conflicts
0xb244e6c4…331a
0x34b655…2a6f
6 touches
3 conflicts
0x609a25a3…8785
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity