← previous blocknext block →recent activity
Analyzing
Block #87,497,171
22 transactions · 18 stateful · 2026-07-13 13:51:57 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,497,171 · 22 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
2w03w14w05w06w112w113w214w316w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326d4924…1788
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0x54b193ad…c830
0x34b655…2a6f
8 touches
6 conflicts
0xa505051b…0632
0x34b655…2a6f
6 touches
3 conflicts
0x0da39371…1ecd
0x34b655…2a6f
6 touches
3 conflicts
0x6d7ccda6…20d2
0x34b655…2a6f
6 touches
3 conflicts
0xcfcb8911…e9da
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x326d4924ab…7f1788
Audit this contract →
← previous block·next block →recent activity