← previous blocknext block →recent activity
Analyzing
Block #84,290,813
14 transactions · 12 stateful · 2026-06-28 17:11:13 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,290,813 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8edd456e…c7e3
0x0555e3…2b9c
2 touches
0 conflicts
0xa554be53…01cc
0x0555e3…2b9c
2 touches
0 conflicts
0x66de0ce3…337a
0x188d58…ea8e
2 touches
0 conflicts
0x66de0ce3…337b
0x188d58…ea8e
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity