← previous blocknext block →recent activity
Analyzing
Block #86,315,193
23 transactions · 20 stateful · 2026-07-08 02:08:52 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,315,193 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w012w015w116w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xccdc4bad…55ad
0x851145…3f07
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xad12c5ec…a5fd
0xd32edf…ff58
3 touches
1 conflict
0x5e038ff2…3a4f
0x40c49f…2af0
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 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
1 conflict on slot 0x16a8cd0cae…8827bd
Audit this contract →
← previous block·next block →recent activity