← previous blocknext block →recent activity
Analyzing
Block #97,547,869
12 transactions · 11 stateful · 2026-08-20 05:55:58 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,547,869 · 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
1w05w06w08w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38a1e34…37c3
0x34b655…2a6f
4 touches
1 conflict
0xbb2238fd…2292
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1ab4c88c…49f3
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xcf17589f…048c
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 0xc38a1e3492…2d37c3
Audit this contract →
← previous block·next block →recent activity