← previous blocknext block →recent activity
Analyzing
Block #84,572,847
57 transactions · 32 stateful · 2026-06-30 00:31:58 UTC
Parallelism
93/100
Blocked
53%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,572,847 · 57 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
1w02w14w06w08w011w112w115w023w129w231w032w233w334w035w136w140w141w144w145w046w247w248w351w052w155w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4e544201…5e2f
0x5afd3e…7620
4 touches
1 conflict
0xafda02a8…1aec
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity