← previous blocknext block →recent activity
Analyzing
Block #84,350,095
12 transactions · 12 stateful · 2026-06-28 23:46:12 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,350,095 · 12 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
1w02w03w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0bea4b38…33e3
0x065c9d…c394
2 touches
0 conflicts
0x28c24eb1…bba7
0x065c9d…c394
2 touches
0 conflicts
0x87378652…c462
0x065c9d…c394
2 touches
0 conflicts
0x9a2199a4…7084
0x065c9d…c394
2 touches
0 conflicts
0xae415f37…e479
0x065c9d…c394
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity