← previous blocknext block →recent activity
Analyzing
Block #84,249,508
16 transactions · 13 stateful · 2026-06-28 12:36:03 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,249,508 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w111w012w113w114w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93d680fb…ac21
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0x7c5260f4…bd96
0xa6afd3…d132
4 touches
1 conflict
0x99246de6…5bd5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
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 0x93d680fb3b…fdac21
Audit this contract →
← previous block·next block →recent activity