← previous blocknext block →recent activity
Analyzing
Block #84,492,451
18 transactions · 18 stateful · 2026-06-29 15:35:19 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,492,451 · 18 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
1w02w13w14w25w06w18w011w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfee13cc…8246
0xa70f46…7777
4 touches
4 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x12a9b76e…cb76
0x3bd359…433a
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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: 0xa70f4653…c87777
4 conflicts on slot 0xcfee13ccf0…b98246
Audit this contract →
← previous block·next block →recent activity