← previous blocknext block →recent activity
Analyzing
Block #86,292,722
15 transactions · 12 stateful · 2026-07-07 23:38:42 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,292,722 · 15 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
1w02w13w14w06w17w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x2a710024…28f7
0xd32edf…ff58
3 touches
1 conflict
0xad814e7e…4504
0x065c9d…c394
2 touches
0 conflicts
0xf8582d70…1a05
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity