← previous blocknext block →recent activity
Analyzing
Block #80,930,941
19 transactions · 16 stateful · 2026-06-13 03:36:10 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,930,941 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3655f976…ac0e
0x065c9d…c394
2 touches
0 conflicts
0x44d048ca…ac55
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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