← previous blocknext block →recent activity
Analyzing
Block #81,102,217
17 transactions · 13 stateful · 2026-06-13 22:37:38 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,102,217 · 17 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
1w02w13w27w311w4
- 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
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x329f2f7d…dcff
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