← previous blocknext block →recent activity
Analyzing
Block #87,713,172
21 transactions · 21 stateful · 2026-07-14 13:57:15 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,713,172 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w19w213w014w115w216w317w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x91462fad…5949
0x34b655…2a6f
4 touches
1 conflict
0x131a4489…c12c
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa4b99367…4050
0x34b655…2a6f
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity