← previous blocknext block →recent activity
Analyzing
Block #86,047,235
18 transactions · 16 stateful · 2026-07-06 20:20:14 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,047,235 · 18 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
2w03w14w05w18w09w110w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x30fa662a…06e0
0x34b655…2a6f
4 touches
1 conflict
0x9d0e7d70…2f12
0x065c9d…c394
3 touches
1 conflict
0x40c0484d…8194
0x188d58…ea8e
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: 0x04fdeac2…f747d7
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity