← previous blocknext block →recent activity
Analyzing
Block #98,273,470
12 transactions · 12 stateful · 2026-08-22 19:14:50 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,273,470 · 12 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
1w05w06w18w29w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x626a04dc…7c7e
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x44f26cbe…58c2
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
3 conflicts on slot 0x626a04dcd9…697c7e
Audit this contract →
← previous block·next block →recent activity