← previous blocknext block →recent activity
Analyzing
Block #86,247,548
13 transactions · 11 stateful · 2026-07-07 18:37:15 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,247,548 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x639c3654…ffc2
0x34b655…2a6f
4 touches
1 conflict
0xca411fd0…9734
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x2ad3919d…524e
0x065c9d…c394
4 touches
1 conflict
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
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 0x639c36546e…c2ffc2
Audit this contract →
← previous block·next block →recent activity