← previous blocknext block →recent activity
Analyzing
Block #97,519,718
19 transactions · 17 stateful · 2026-08-20 03:34:22 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,519,718 · 19 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
1w02w06w09w110w115w016w117w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc158f1d9…bc17
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
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
3 conflicts on slot 0xc158f1d988…ebbc17
Audit this contract →
← previous block·next block →recent activity