← previous blocknext block →recent activity
Analyzing
Block #81,445,261
23 transactions · 20 stateful · 2026-06-15 12:41:42 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,445,261 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w27w38w412w013w115w216w018w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5d7e85d…b578
0x40c49f…2af0
6 touches
3 conflicts
0x897df0ee…b0c5
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x48a29a03…c43c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
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: 0x40c49f17…d22af0
3 conflicts on slot 0xc5d7e85db7…01b578
Audit this contract →
← previous block·next block →recent activity