← previous blocknext block →recent activity
Analyzing
Block #84,059,441
15 transactions · 12 stateful · 2026-06-27 15:30:12 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,059,441 · 15 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
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x489bff18…82f3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9f9b
0x16f70c…c3dd
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x3ab5f972…0a02
0x34b655…2a6f
2 touches
0 conflicts
0x42b49e24…6270
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity