← previous blocknext block →recent activity
Analyzing
Block #84,073,581
22 transactions · 19 stateful · 2026-06-27 17:04:12 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,073,581 · 22 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
1w02w13w06w07w19w112w013w214w215w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
8 touches
6 conflicts
0x62d6e82b…a750
0x34b655…2a6f
6 touches
3 conflicts
0xa3010808…6585
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x49194594…2c70
0x34b655…2a6f
4 touches
1 conflict
0x4cc838ad…4525
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: Perpl
6 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity