← previous blocknext block →recent activity
Analyzing
Block #86,246,272
19 transactions · 14 stateful · 2026-07-07 18:28:42 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,246,272 · 19 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
2w03w15w06w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb274cb13…808b
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x85fed3a2…a604
0x34b655…2a6f
2 touches
0 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
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 0xb274cb134d…a9808b
Audit this contract →
← previous block·next block →recent activity