← previous blocknext block →recent activity
Analyzing
Block #87,421,307
17 transactions · 12 stateful · 2026-07-13 05:24:41 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,421,307 · 17 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
1w02w18w09w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92a2c049…0ed8
0x34b655…2a6f
4 touches
1 conflict
0xd8eed7e0…c96e
0x34b655…2a6f
4 touches
1 conflict
0xd69f26b4…c204
0x2a68ba…90c5
4 touches
1 conflict
0x7701846c…9b82
0x851145…3f07
4 touches
1 conflict
0x8b181a93…d4a7
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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: Perpl
1 conflict on slot 0x92a2c04910…330ed8
Audit this contract →
← previous block·next block →recent activity