← previous blocknext block →recent activity
Analyzing
Block #84,100,664
10 transactions · 8 stateful · 2026-06-27 20:04:50 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,100,664 · 10 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
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebbcae2a…16f8
0x34b655…2a6f
4 touches
1 conflict
0xa49043a3…6035
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd95e9685…0457
0x34b655…2a6f
3 touches
1 conflict
0x5e289b76…8e57
0x34b655…2a6f
3 touches
1 conflict
0x357e5c5b…0aaf
0x40c49f…2af0
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 0xebbcae2a12…8416f8
Audit this contract →
← previous block·next block →recent activity