← previous blocknext block →recent activity
Analyzing
Block #84,047,273
21 transactions · 19 stateful · 2026-06-27 14:09:01 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,047,273 · 21 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
1w09w011w112w213w114w317w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32359294…7113
0x34b655…2a6f
6 touches
3 conflicts
0x3de5fb8b…400a
0xa6afd3…d132
4 touches
1 conflict
0x1d2a8430…30bf
0xa6afd3…d132
4 touches
1 conflict
0xe3b308a8…87fa
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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
3 conflicts on slot 0x3235929431…327113
Audit this contract →
← previous block·next block →recent activity