← previous blocknext block →recent activity
Analyzing
Block #87,045,364
19 transactions · 18 stateful · 2026-07-11 11:30:50 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,045,364 · 19 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
2w03w15w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0x9d1bb389…c7d9
0xb1dbf0…c0d3
4 touches
1 conflict
0xb76f7c01…c3a5
0x34b655…2a6f
4 touches
1 conflict
0x8d0d8061…d410
0xc8689a…ee79
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x727fbce7…0c80
0x34b655…2a6f
2 touches
0 conflicts
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 0x8a35acfbc1…6bd1aa
Audit this contract →
← previous block·next block →recent activity