← previous blocknext block →recent activity
Analyzing
Block #98,063,264
21 transactions · 19 stateful · 2026-08-22 01:36:32 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,063,264 · 21 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
1w04w06w07w19w112w118w219w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x7a520ce4…b3a6
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0c89c370…e9ef
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
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: 0x34014398…d1768f
1 conflict on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity