← previous blocknext block →recent activity
Analyzing
Block #84,539,073
17 transactions · 13 stateful · 2026-06-29 20:46:14 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,539,073 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w111w013w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7763f6…89be
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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 0x1c7763f6c9…dd89be
Audit this contract →
← previous block·next block →recent activity