← previous blocknext block →recent activity
Analyzing
Block #98,023,323
24 transactions · 18 stateful · 2026-08-21 22:15:30 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,023,323 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w011w012w113w215w019w321w422w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x04a837dd…e245
0x34b655…2a6f
4 touches
1 conflict
0x104887dc…9894
0x34b655…2a6f
4 touches
1 conflict
0x1952c598…df64
0x34b655…2a6f
4 touches
1 conflict
0x1d731f70…4557
0x34b655…2a6f
4 touches
1 conflict
0x1e9fccc4…5c21
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity