← previous blocknext block →recent activity
Analyzing
Block #86,354,291
16 transactions · 15 stateful · 2026-07-08 06:29:57 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,354,291 · 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
1w06w08w19w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x99ecae25…abb9
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbe3aa12a…0258
0x065c9d…c394
2 touches
0 conflicts
0xc4131ee0…dcb8
0x065c9d…c394
2 touches
0 conflicts
0xfb8e623a…607b
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 0x2d071de0f2…94c86e
Audit this contract →
← previous block·next block →recent activity