← previous blocknext block →recent activity
Analyzing
Block #84,622,139
18 transactions · 16 stateful · 2026-06-30 06:00:19 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,622,139 · 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
1w02w13w14w28w09w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a489c9e…16ab
0x34b655…2a6f
6 touches
3 conflicts
0x97fe3267…5e87
0x34b655…2a6f
6 touches
3 conflicts
0xb44d5376…33cc
0x34b655…2a6f
6 touches
3 conflicts
0x939f4f84…23cb
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Perpl
3 conflicts on slot 0x3a489c9ee1…9c16ab
Audit this contract →
← previous block·next block →recent activity