← previous blocknext block →recent activity
Analyzing
Block #84,358,265
16 transactions · 16 stateful · 2026-06-29 00:40:45 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,358,265 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x4fea56c7…fbba
0x5afd3e…7620
2 touches
0 conflicts
0x7f736aa1…6cef
0x5afd3e…7620
2 touches
0 conflicts
0x9879fe14…e154
0x5afd3e…7620
2 touches
0 conflicts
0xe78637be…65db
0x5afd3e…7620
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
1 conflict on slot 0x5581d709b4…95ab77
Audit this contract →
← previous block·next block →recent activity