← previous blocknext block →recent activity
Analyzing
Block #87,045,873
19 transactions · 16 stateful · 2026-07-11 11:34:14 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.37
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,045,873 · 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
1w03w05w19w110w012w013w014w115w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x6e22d6fd…5610
0x065c9d…c394
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 0x793aa64d0d…fdb09d
Audit this contract →
← previous block·next block →recent activity