← previous blocknext block →recent activity
Analyzing
Block #84,607,669
16 transactions · 12 stateful · 2026-06-30 04:24:03 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,607,669 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x274b85f7…c526
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x448a363c…a731
0x40c49f…2af0
2 touches
0 conflicts
0x6e14ab40…e8a6
0x40c49f…2af0
2 touches
0 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
2 touches
0 conflicts
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
1 conflict on slot 0x274b85f751…f5c526
Audit this contract →
← previous block·next block →recent activity