← previous blocknext block →recent activity
Analyzing
Block #86,222,229
38 transactions · 28 stateful · 2026-07-07 15:48:05 UTC
Parallelism
84/100
Blocked
46%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,222,229 · 38 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
4w05w16w28w39w416w021w122w423w524w025w127w232w233w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x17c44db3…8888
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe6f2ae57…2026
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x431fed…d150
6 touches
3 conflicts
0x00000000…0002
0x431fed…d150
6 touches
3 conflicts
0x00000000…0003
0x431fed…d150
6 touches
3 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: Kuru Exchange: MarginAccount
10 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity