← previous blocknext block →recent activity
Analyzing
Block #84,032,676
23 transactions · 17 stateful · 2026-06-27 12:31:45 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,032,676 · 23 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
1w02w13w04w16w27w311w112w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc8b97d…96da
0x2a68ba…90c5
6 touches
3 conflicts
0x46110204…b617
0x40c49f…2af0
5 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7c5260f4…bd96
0xa6afd3…d132
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 0x9fc8b97d38…9f96da
Audit this contract →
← previous block·next block →recent activity