← previous blocknext block →recent activity
Analyzing
Block #84,334,673
27 transactions · 22 stateful · 2026-06-28 22:03:24 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,334,673 · 27 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
1w02w19w010w111w012w013w115w016w218w219w220w321w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bdcc5ee…7e90
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7b7af531…48f1
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b68e69b…0754
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x75194ada…a1c5
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
3 conflicts on slot 0x4bdcc5eebf…627e90
Audit this contract →
← previous block·next block →recent activity