← previous blocknext block →recent activity
Analyzing
Block #98,434,468
29 transactions · 28 stateful · 2026-08-23 08:44:51 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,434,468 · 29 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
1w03w04w15w26w37w48w510w011w112w213w214w015w118w019w021w123w324w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x3af0dd8e…0024
0x1b6862…e19c
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: 0xbb3f3cb7…74e046
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity