← previous blocknext block →recent activity
Analyzing
Block #80,248,211
16 transactions · 14 stateful · 2026-06-09 23:43:36 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,248,211 · 16 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
1w02w03w14w25w37w013w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86e6cece…1fd5
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x48d96151…1647
0xa6afd3…d132
2 touches
0 conflicts
0x00000000…0000
0xe5bf0f…7139
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 0x86e6cece3e…391fd5
Audit this contract →
← previous block·next block →recent activity