← previous blocknext block →recent activity
Analyzing
Block #86,314,852
12 transactions · 11 stateful · 2026-07-08 02:06:36 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,314,852 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e02109f…c11b
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5cb4c74e…381e
0x34b655…2a6f
4 touches
1 conflict
0x5cb4c74e…381f
0x34b655…2a6f
4 touches
1 conflict
0x9e5b25dc…0f1e
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x5e02109fed…68c11b
Audit this contract →
← previous block·next block →recent activity