← previous blocknext block →recent activity
Analyzing
Block #86,623,278
18 transactions · 15 stateful · 2026-07-09 12:29:13 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,623,278 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0x4a870d86…79ef
0x336ed4…c59c
4 touches
1 conflict
0xc88f593e…5d93
0x336ed4…c59c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity