← previous blocknext block →recent activity
Analyzing
Block #84,460,985
25 transactions · 19 stateful · 2026-06-29 12:05:21 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,460,985 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w011w112w213w015w016w118w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x59658b83…2229
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3da49e5d…8067
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0x93d680fb…ac21
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 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity