← previous blocknext block →recent activity
Analyzing
Block #87,355,102
16 transactions · 16 stateful · 2026-07-12 22:01:51 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,355,102 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w08w19w210w311w412w114w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a11736c…64a0
0x34b655…2a6f
10 touches
10 conflicts
0xe5ddbbc9…91a7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x198bae6a…f31c
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb0
0x34b655…2a6f
4 touches
1 conflict
0xd94ac4d1…edb1
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
10 conflicts on slot 0x7a11736c7c…8b64a0
Audit this contract →
← previous block·next block →recent activity