← previous blocknext block →recent activity
Analyzing
Block #84,563,137
17 transactions · 16 stateful · 2026-06-29 23:27:14 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,563,137 · 17 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
1w02w13w25w06w17w28w09w111w113w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa20c96e3…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x6637e421…af93
0x34b655…2a6f
6 touches
3 conflicts
0x97b0b2ee…4666
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xcad937e9…7872
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity