← previous blocknext block →recent activity
Analyzing
Block #84,538,673
21 transactions · 11 stateful · 2026-06-29 20:43:35 UTC
Parallelism
90/100
Blocked
27%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,538,673 · 21 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
1w06w07w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0xfff39462…a61b
0x34b655…2a6f
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0xd8f843e1…182e
0xa6afd3…d132
4 touches
1 conflict
0x5f425f2f…7fe4
0xa6afd3…d132
3 touches
1 conflict
0x6f36a742…687d
0xa6afd3…d132
3 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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity