← previous blocknext block →recent activity
Analyzing
Block #87,420,929
8 transactions · 8 stateful · 2026-07-13 05:22:10 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,420,929 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa3bf02ae…ccd8
0x065c9d…c394
3 touches
1 conflict
0xe5443a10…19d1
0x065c9d…c394
3 touches
1 conflict
0x296f884a…e619
0x065c9d…c394
3 touches
1 conflict
0x198a44fd…98d2
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x2be09ff3…ce49
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xa4f8097941…fd4d71
Audit this contract →
← previous block·next block →recent activity