← previous blocknext block →recent activity
Analyzing
Block #97,185,470
10 transactions · 8 stateful · 2026-08-18 23:00:28 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,185,470 · 10 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x31f6cdda…d22b
0x34b655…2a6f
4 touches
1 conflict
0xda49f6b4…2482
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x26cc90bf…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…669f
0x34b655…2a6f
2 touches
0 conflicts
0x362894e6…66a0
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 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity