← previous blocknext block →recent activity
Analyzing
Block #84,599,182
9 transactions · 8 stateful · 2026-06-30 03:27:22 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,599,182 · 9 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x19a51b86…0a59
0x065c9d…c394
4 touches
1 conflict
0x94e84193…dbf6
0x065c9d…c394
3 touches
1 conflict
0xa7f961d8…86d9
0x065c9d…c394
3 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x32359294…7113
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
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