← previous blocknext block →recent activity
Analyzing
Block #97,494,104
12 transactions · 12 stateful · 2026-08-20 01:25:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,494,104 · 12 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
1w03w05w18w29w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0x5e87c571…1edc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x3e34afa7…4710
0x34b655…2a6f
2 touches
0 conflicts
0x4c220546…e3b0
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
3 conflicts on slot 0xda1f3e2ca4…a6b73d
Audit this contract →
← previous block·next block →recent activity