← previous blocknext block →recent activity
Analyzing
Block #87,628,449
18 transactions · 15 stateful · 2026-07-14 04:30:45 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,628,449 · 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
2w03w15w06w18w09w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9cbb059…9e23
0x34b655…2a6f
4 touches
1 conflict
0x98afad44…850d
0x34b655…2a6f
4 touches
1 conflict
0xba327b58…b790
0x34b655…2a6f
4 touches
1 conflict
0xbd66754d…4f4a
0x34b655…2a6f
4 touches
1 conflict
0xbd66754d…4f4b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8f4deb0…dcf3
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xc9cbb059e2…659e23
Audit this contract →
← previous block·next block →recent activity