← previous blocknext block →recent activity
Analyzing
Block #84,574,069
11 transactions · 7 stateful · 2026-06-30 00:40:08 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,574,069 · 11 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
3w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7f93f2f0…6666
0x34b655…2a6f
4 touches
1 conflict
0xaf1d00c2…c702
0x34b655…2a6f
4 touches
1 conflict
0xf1e0175c…5649
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x06387bd2…4a83
0x34b655…2a6f
4 touches
1 conflict
0x4de565d3…ae16
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity