← previous blocknext block →recent activity
Analyzing
Block #97,562,002
19 transactions · 19 stateful · 2026-08-20 07:08:15 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,562,002 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w26w311w416w117w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x613be9af…61ea
0x34b655…2a6f
10 touches
10 conflicts
0xcc02d79e…7e86
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x1c124aea…e94d
0x34b655…2a6f
4 touches
1 conflict
0x275ce6ab…730a
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
10 conflicts on slot 0x613be9af53…c661ea
Audit this contract →
← previous block·next block →recent activity