← previous blocknext block →recent activity
Analyzing
Block #84,058,807
17 transactions · 15 stateful · 2026-06-27 15:26:00 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,058,807 · 17 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
1w05w06w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x68eef65a…a86d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa6c9a33e…d839
0x34b655…2a6f
4 touches
1 conflict
0x763dd151…d9de
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
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
1 conflict on slot 0x664bf99ec8…ec0a8c
Audit this contract →
← previous block·next block →recent activity