← previous blocknext block →recent activity
Analyzing
Block #87,594,043
21 transactions · 18 stateful · 2026-07-14 00:40:39 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,594,043 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w213w314w415w416w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5e6e5ee…9fb2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb543d97e…cc3f
0x34b655…2a6f
4 touches
1 conflict
0xbe1968df…0378
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x02679875…8d2f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0xd5e6e5eef3…f19fb2
Audit this contract →
← previous block·next block →recent activity