← previous blocknext block →recent activity
Analyzing
Block #81,028,389
18 transactions · 16 stateful · 2026-06-13 14:25:19 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,028,389 · 18 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7b3f837f…1cc2
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x23ac5fbe…e09b
0x40c49f…2af0
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 0x6d383d1fcb…18a65e
Audit this contract →
← previous block·next block →recent activity