← previous blocknext block →recent activity
Analyzing
Block #81,632,824
11 transactions · 11 stateful · 2026-06-16 09:31:08 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,632,824 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb7cf32e8…3fc6
0x065c9d…c394
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
4 touches
1 conflict
0xbf62f7be…e672
0x065c9d…c394
3 touches
1 conflict
0xe1296edb…a18d
0x065c9d…c394
3 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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