← previous blocknext block →recent activity
Analyzing
Block #98,063,265
18 transactions · 16 stateful · 2026-08-22 01:36:32 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,063,265 · 18 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
1w03w04w15w27w08w19w010w111w313w216w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14def591…385e
0x851145…3f07
6 touches
3 conflicts
0xc6174640…66c9
0x851145…3f07
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xe957c63b…e347
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x80caf0f7…f2de
0x2b46c0…1669
4 touches
1 conflict
0x8b2c44b4…7e59
0x2b46c0…1669
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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: 0x851145ea…9f3f07
3 conflicts on slot 0x14def5910f…6e385e
Audit this contract →
← previous block·next block →recent activity