← previous blocknext block →recent activity
Analyzing
Block #86,491,591
16 transactions · 13 stateful · 2026-07-08 21:47:40 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,491,591 · 16 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
1w02w14w05w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaaf3fcda…ac44
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x352a4ae4…d8db
0x40c49f…2af0
2 touches
0 conflicts
0x4873dccb…0b4e
0x40c49f…2af0
2 touches
0 conflicts
0xd5797db0…8720
0x40c49f…2af0
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 0xaaf3fcda13…c7ac44
Audit this contract →
← previous block·next block →recent activity