← previous blocknext block →recent activity
Analyzing
Block #81,028,342
12 transactions · 8 stateful · 2026-06-13 14:25:00 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,028,342 · 12 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5612fda6…3047
0x065c9d…c394
4 touches
1 conflict
0xd0b4724c…709f
0x065c9d…c394
3 touches
1 conflict
0xc09ca699…5301
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5486729a…488f
0x065c9d…c394
2 touches
0 conflicts
0x76f17bc9…5ab6
0x065c9d…c394
2 touches
0 conflicts
0xcdc85fd3…d22b
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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: Market-MON/USDC
1 conflict on slot 0x5612fda680…8c3047
Audit this contract →
← previous block·next block →recent activity