← previous blocknext block →recent activity
Analyzing
Block #87,167,269
16 transactions · 13 stateful · 2026-07-12 01:05:00 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,167,269 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1ed670e…9e0b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd44701be…2942
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
4 touches
1 conflict
0x0712100b…e8bc
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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 0xe1ed670e1b…a39e0b
Audit this contract →
← previous block·next block →recent activity