← previous blocknext block →recent activity
Analyzing
Block #86,514,008
16 transactions · 14 stateful · 2026-07-09 00:17:10 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,514,008 · 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
2w03w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30d68101…0ed2
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x01c408dd…4368
0x34b655…2a6f
4 touches
1 conflict
0x43081395…4e15
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0xcba60f5c…5254
0x065c9d…c394
2 touches
0 conflicts
0xd83d9ecd…851f
0x065c9d…c394
2 touches
0 conflicts
0xfc857eab…3984
0x065c9d…c394
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 0x30d6810120…c30ed2
Audit this contract →
← previous block·next block →recent activity