← previous blocknext block →recent activity
Analyzing
Block #84,047,870
16 transactions · 14 stateful · 2026-06-27 14:13:00 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,047,870 · 16 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
1w05w06w17w28w111w313w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e388d02…e460
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0x40c49f17…d22af0
3 conflicts on slot 0x0e388d0269…4ee460
Audit this contract →
← previous block·next block →recent activity