← previous blocknext block →recent activity
Analyzing
Block #86,194,246
15 transactions · 15 stateful · 2026-07-07 12:41:11 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,194,246 · 15 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
1w02w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90ee334b…01e7
0x34b655…2a6f
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda8d6085…7b09
0x34b655…2a6f
4 touches
1 conflict
0xb31e0369…020b
0x34b655…2a6f
4 touches
1 conflict
0x3ed7aac0…8f80
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
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
1 conflict on slot 0x90ee334b8b…2501e7
Audit this contract →
← previous block·next block →recent activity