← previous blocknext block →recent activity
Analyzing
Block #97,430,039
12 transactions · 10 stateful · 2026-08-19 20:02:37 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,430,039 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w07w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35ea602c…019a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x3199a6b2…eb67
0xa6afd3…d132
4 touches
1 conflict
0x342ec28c…cd7f
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x3b499e79…b551
0x34b655…2a6f
2 touches
0 conflicts
0x4bda18d7…12f3
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 0x35ea602c56…c2019a
Audit this contract →
← previous block·next block →recent activity