← previous blocknext block →recent activity
Analyzing
Block #81,480,013
12 transactions · 9 stateful · 2026-06-15 16:33:19 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,480,013 · 12 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
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xcb37f317…3620
0x065c9d…c394
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0x8ef7a1b3…b934
0x40c49f…2af0
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x47bae1…7568
2 touches
0 conflicts
0x00000000…0002
0x47bae1…7568
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity