← previous blocknext block →recent activity
Analyzing
Block #86,316,449
12 transactions · 11 stateful · 2026-07-08 02:17:15 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,316,449 · 12 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
1w02w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cb4c74e…381e
0x34b655…2a6f
4 touches
1 conflict
0x5cb4c74e…381f
0x34b655…2a6f
4 touches
1 conflict
0x65f773b6…46cc
0x34b655…2a6f
4 touches
1 conflict
0x81681867…64fa
0x34b655…2a6f
4 touches
1 conflict
0x8a5ced1c…3b29
0x34b655…2a6f
4 touches
1 conflict
0xca411fd0…9734
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x5cb4c74e46…b8381e
Audit this contract →
← previous block·next block →recent activity