← previous blocknext block →recent activity
Analyzing
Block #84,290,931
13 transactions · 13 stateful · 2026-06-28 17:12:01 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,290,931 · 13 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
5w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ec469b8…d790
0x34b655…2a6f
2 touches
0 conflicts
0x19007011…d3df
0x34b655…2a6f
2 touches
0 conflicts
0x1c124aea…e94d
0x34b655…2a6f
2 touches
0 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
2 touches
0 conflicts
0x25cb9e65…a6cc
0x34b655…2a6f
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity