← previous blocknext block →recent activity
Analyzing
Block #81,630,528
29 transactions · 25 stateful · 2026-06-16 09:15:50 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,630,528 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w310w011w112w013w118w419w020w121w224w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x0cc9b2…7777
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xb428a976…7cf0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
6 touches
3 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: MONI (MONI)
3 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity