← previous blocknext block →recent activity
Analyzing
Block #98,066,545
64 transactions · 62 stateful · 2026-08-22 01:53:03 UTC
Parallelism
94/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,066,545 · 64 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w059w060w161w262w363w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
0x34b655…2a6f
4 touches
1 conflict
0xc6f3c5a3…3faa
0x34b655…2a6f
3 touches
1 conflict
0x1d6ce97a…901b
0x34b655…2a6f
3 touches
1 conflict
0x2f74f175…9289
0x2b46c0…1669
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity