← previous blocknext block →recent activity
Analyzing
Block #86,715,434
16 transactions · 14 stateful · 2026-07-09 22:45:47 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,715,434 · 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
1w02w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd94ac4d1…edb1
0x34b655…2a6f
4 touches
1 conflict
0xfd1b3222…bff6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb0
0x34b655…2a6f
4 touches
1 conflict
0x5f7e17b8…9be6
0x40c49f…2af0
2 touches
0 conflicts
0xa70a594f…6b41
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 0xd94ac4d151…3cedb1
Audit this contract →
← previous block·next block →recent activity