← previous blocknext block →recent activity
Analyzing
Block #84,037,856
13 transactions · 11 stateful · 2026-06-27 13:06:20 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,037,856 · 13 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
2w03w15w06w27w38w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939a5d3a…3c36
0x34b655…2a6f
4 touches
1 conflict
0xce8c5913…6d21
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9540632c…78a0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
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 0x939a5d3aac…c43c36
Audit this contract →
← previous block·next block →recent activity