← previous blocknext block →recent activity
Analyzing
Block #87,419,417
30 transactions · 23 stateful · 2026-07-13 05:12:04 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,419,417 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w111w112w213w314w415w518w221w626w327w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab360ba6…efc4
0x34b655…2a6f
8 touches
6 conflicts
0x87fc64a7…aed6
0xd32edf…ff58
7 touches
6 conflicts
0x88413c1a…7783
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x56091b00…b694
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xab360ba6a4…ffefc4
Audit this contract →
← previous block·next block →recent activity