← previous blocknext block →recent activity
Analyzing
Block #84,063,932
31 transactions · 27 stateful · 2026-06-27 16:00:03 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,063,932 · 31 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
1w03w04w112w013w014w115w116w017w118w219w020w121w222w225w126w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0161
0xd45826…f134
6 touches
3 conflicts
0x8ebf69ec…edcd
0xd45826…f134
6 touches
3 conflicts
0x8ebf69ec…edd2
0xd45826…f134
6 touches
3 conflicts
0x00000000…00fc
0xd45826…f134
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x87f7111a…b2ab
0x34b655…2a6f
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: 0xd458261e…e6f134
3 conflicts on slot 0x0000000000…000161
Audit this contract →
← previous block·next block →recent activity