← previous blocknext block →recent activity
Analyzing
Block #84,352,935
18 transactions · 18 stateful · 2026-06-29 00:05:11 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,352,935 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w09w112w013w115w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0xd6d4eb00…30f3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x0494780e…2900
0x8fbe07…71b6
4 touches
1 conflict
0xa6fd7409…16b7
0x8fbe07…71b6
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: 0xdde00377…29c9a4
1 conflict on slot 0xb983f9fc1c…ab9b91
Audit this contract →
← previous block·next block →recent activity