← previous blocknext block →recent activity
Analyzing
Block #87,284,833
14 transactions · 14 stateful · 2026-07-12 14:12:00 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,284,833 · 14 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
5w06w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0xb02c6b4b…5b1e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc89dfdc7…8595
0x34b655…2a6f
4 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
4 touches
1 conflict
0xe8058ec4…ebac
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 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity