← previous blocknext block →recent activity
Analyzing
Block #86,247,973
33 transactions · 27 stateful · 2026-07-07 18:40:06 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,247,973 · 33 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
1w02w04w07w18w09w113w014w116w017w118w220w221w123w225w326w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0xf8873dd8…79dc
0x065c9d…c394
6 touches
3 conflicts
0x074b59c9…255d
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0001
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity