← previous blocknext block →recent activity
Analyzing
Block #87,666,740
27 transactions · 23 stateful · 2026-07-14 08:46:35 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,666,740 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w010w011w113w214w215w116w318w420w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24f6d4ca…c33b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x06c980ab…5577
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x8be39390…47fd
0x34b655…2a6f
4 touches
1 conflict
0xb7b28ab0…40d1
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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
6 conflicts on slot 0x24f6d4ca30…1ec33b
Audit this contract →
← previous block·next block →recent activity