← previous blocknext block →recent activity
Analyzing
Block #84,501,129
27 transactions · 24 stateful · 2026-06-29 16:33:14 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,501,129 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w07w18w29w310w411w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0xe2e45419…f17b
0x34b655…2a6f
10 touches
10 conflicts
0x63d3f410…7149
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0x5df6102c…6494
0xa6afd3…d132
8 touches
6 conflicts
0x7b7af531…48f1
0xa6afd3…d132
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
8 touches
6 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: 0xd637b38f…c64160
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity