← previous blocknext block →recent activity
Analyzing
Block #86,491,546
23 transactions · 18 stateful · 2026-07-08 21:47:22 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,491,546 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w09w113w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x540fdd33…3c5e
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0005
0x5afd3e…7620
2 touches
0 conflicts
0x1535cd34…e342
0x5afd3e…7620
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x540fdd3362…0b3c5e
Audit this contract →
← previous block·next block →recent activity