← previous blocknext block →recent activity
Analyzing
Block #84,190,236
11 transactions · 10 stateful · 2026-06-28 06:00:59 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,190,236 · 11 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
1w03w14w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xf1dc16b5…fb0b
0x065c9d…c394
4 touches
1 conflict
0xdde8af9d…1bef
0x34b655…2a6f
4 touches
1 conflict
0xf33e4b5b…f860
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1fd7f710…9437
0x34b655…2a6f
3 touches
1 conflict
0x919e00fa…72d7
0x34b655…2a6f
3 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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity