← previous blocknext block →recent activity
Analyzing
Block #87,341,163
16 transactions · 15 stateful · 2026-07-12 20:28:40 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,341,163 · 16 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
2w03w14w05w06w17w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0xf6dfaa05…2749
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa7013be2…c0a8
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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x6a248bdcb5…023c1b
Audit this contract →
← previous block·next block →recent activity