← previous blocknext block →recent activity
Analyzing
Block #84,610,183
14 transactions · 12 stateful · 2026-06-30 04:40:47 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,610,183 · 14 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
1w02w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x2baef3d5…1813
0x40c49f…2af0
2 touches
0 conflicts
0x72e14745…479d
0x40c49f…2af0
2 touches
0 conflicts
0x73faa861…0ff3
0x40c49f…2af0
2 touches
0 conflicts
0xdbdcb8bd…cdb9
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 0x97c6748621…2727fe
Audit this contract →
← previous block·next block →recent activity