← previous blocknext block →recent activity
Analyzing
Block #97,613,259
20 transactions · 18 stateful · 2026-08-20 11:27:56 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,613,259 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w111w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf238da31…f35f
0x34b655…2a6f
4 touches
1 conflict
0x093ac07c…bd27
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x5ea141c8…7f6b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
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
1 conflict on slot 0xf238da3130…00f35f
Audit this contract →
← previous block·next block →recent activity