← previous blocknext block →recent activity
Analyzing
Block #84,365,301
10 transactions · 10 stateful · 2026-06-29 01:27:40 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,365,301 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc162ad99…8c0d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x44b39b23…f1b7
0x40c49f…2af0
2 touches
0 conflicts
0xc7c7cfb7…237e
0x40c49f…2af0
2 touches
0 conflicts
0xda01d21e…740e
0x40c49f…2af0
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: 0x40c49f17…d22af0
3 conflicts on slot 0xc162ad9929…518c0d
Audit this contract →
← previous block·next block →recent activity