← previous blocknext block →recent activity
Analyzing
Block #85,138,543
16 transactions · 14 stateful · 2026-07-02 15:25:12 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,138,543 · 16 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe47478a3…a058
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x45dc6a93…630b
0x40c49f…2af0
2 touches
0 conflicts
0x5dffbd97…d049
0x40c49f…2af0
2 touches
0 conflicts
0xe78bb6f7…d37b
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 0xe47478a3e7…67a058
Audit this contract →
← previous block·next block →recent activity