← previous blocknext block →recent activity
Analyzing
Block #87,347,723
16 transactions · 16 stateful · 2026-07-12 21:12:31 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,347,723 · 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
2w03w17w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc009105d…96f7
0xb1dbf0…c0d3
4 touches
1 conflict
0x33d170e2…2c61
0x34b655…2a6f
4 touches
1 conflict
0x33d170e2…2c62
0x34b655…2a6f
4 touches
1 conflict
0x4c623175…29e4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x94b8e9d6…77d6
0x34b655…2a6f
4 touches
1 conflict
0xa83171b3…432d
0x34b655…2a6f
4 touches
1 conflict
0x50e10826…843b
0xb1dbf0…c0d3
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 0xc009105db3…e996f7
Audit this contract →
← previous block·next block →recent activity