← previous blocknext block →recent activity
Analyzing
Block #84,527,496
12 transactions · 11 stateful · 2026-06-29 19:29:04 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,527,496 · 12 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
4w05w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1aad6e5…9135
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x54b224b4…4fb8
0x1efe02…37d6
2 touches
0 conflicts
0xd39a1b38…dd72
0x2880ab…7b43
2 touches
0 conflicts
0xd39a1b38…dd73
0x2880ab…7b43
2 touches
0 conflicts
0x2f3b176f…3411
0x34b655…2a6f
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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 0xc1aad6e5d4…f89135
Audit this contract →
← previous block·next block →recent activity