← previous blocknext block →recent activity
Analyzing
Block #84,490,071
12 transactions · 11 stateful · 2026-06-29 15:19:24 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,490,071 · 12 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
1w02w14w05w16w27w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7add284…8d28
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
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 0xd7add284d9…568d28
Audit this contract →
← previous block·next block →recent activity