← previous blocknext block →recent activity
Analyzing
Block #80,100,809
11 transactions · 7 stateful · 2026-06-09 07:21:02 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,100,809 · 11 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
5w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xe6dc9e4c…0bd5
0x96b79e…d00a
4 touches
1 conflict
0x3f0793e5…6457
0x065c9d…c394
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
2 touches
0 conflicts
0xedb848fe…6534
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 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity