← previous blocknext block →recent activity
Analyzing
Block #97,536,739
14 transactions · 13 stateful · 2026-08-20 04:59:59 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,536,739 · 14 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
1w03w06w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3315ffd1…722e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0x3a874400…e10d
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
0x34b655…2a6f
2 touches
0 conflicts
0x86cea35b…bdff
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 0x3315ffd1bf…5d722e
Audit this contract →
← previous block·next block →recent activity